Method and apparatus for a messaging protocol within a distributed telecommunications architecture

ABSTRACT

A method for message handling in a telecommunications system having a network services processor (NSP) for accessing, processing, and distributing telecommunications in conformance with a predefined signaling system and for distributing processing applications including call handling and routing to a plurality of platforms, each platform having a unique address and responds to application specific messages, the method comprising: connecting the plurality of platforms to local area networks (LANs), the plurality of platforms include packet managers (PMs) for accessing, processing, and distributing packetized call data over a packet network and a plurality of media control platforms (MCPs) for accessing, processing, and distributing media tasks (MCTs); connecting the LANs to a corresponding plurality of interconnect controllers (ICCs), each ICC for interfacing the NSP with the plurality of platforms through a corresponding LAN; and distributing application specific messages to the plurality of platforms via a message protocol (hiQ) having a message frame which encapsulates application specific messages within a standard LAN protocol.

CONTINUATION DATA

This application claims the benefit of priority under 35 U.S.C. 119(e)to two copending U.S. Patent Provisional Applications, Ser. Nos.60/279,295 and 60/279,279, both filed on Mar. 28, 2001, the contents ofeach of said applications being incorporated herein by reference.

This application is also related to the following U.S. patentapplications: U.S. patent application Ser. No. 10/109,293 filed Mar. 28,2002 entitled Distributed Architecture for a Telecommunications SoftwareSwitch; U.S. patent application Ser. No. 10/108,603 filed Mar. 28, 2002entitled Distributed Architecture for a Telecommunications System; U.S.patent application Ser. No. 10/109,196 fired Mar. 28, 2002 entitledMethod and Apparatus for Providing A Software Adaptation Layer in aTelecommunications System; U.S. patent application Ser. No. 10/115,453filed Mar. 28, 2002 entitled Method and Apparatus for a Deriving aStandard MAC Address from A Physical Location; U.S. patent applicationSer. No. 10/109,157 filed Mar. 28, 2002 entitled Method and Apparatusfor A Centralized Maintenance System within a DistributedTelecommunications Architecture; and U.S. patent application Ser. No.10/109,149 filed Mar. 28, 2002 entitled Method and Apparatus forProviding a Proprietary Data Interface in a DistributedTelecommunications System, the contents of each of said applicationsbeing incorporated by reference herein.

BACKGROUND OF THE INVENTION

Digital switching systems are used in telecommunications systems foraccessing, processing, and distributing telecommunications dataincluding voice data and telephone calls. The digital switching systemsare highly complex and for the most part are the result of many years ofevolution and enhancements. A number of digital switching systems madeby different manufacturers are used to handle telecommunications trafficthroughout the world. Because the different manufacturers designed theirsystems with different hardware and software, many components andfunctions of one system are not compatible with another. Even if thesame or similar components and functions were employed, as differentsystems are upgraded with new hardware, architectural modifications andcontinuous development of new or enhanced features, the systems divergein similarity and compatibility.

As global and local call traffic continues to increase, telephonenetwork operators demand increased call handling capacity fromexchanges. A typical exchange in the United States handles about onemillion busy hour call attempts (BHCA). Most switching systems can beupgraded to handle more call capacity. However, many exchanges arealready reaching their capacity in terms of processing capabilities andthe quick-fix type upgrades cannot fulfill the call handling capabilitybeing specified, which calls for capability to handle six million BHCAin present and future systems. System architectural changes andredesigns may be the only long-term solution.

Network operators are therefore desirous of the development of switchingand communication systems having architecture that provide increasedprocessing capabilities but also fit within the existing framework withminimal impact on the required feature set, e.g., having a uniform viewand single-entry point with respect to both an operations perspectiveand a signaling perspective. It is also desirous that the newarchitecture will be able to adapt to commercially available platformsand existing messaging protocols so that significant improvements inthroughput and capacity may be realized by upgrading the platforms asthe improved technology becomes available.

With the increase in capabilities and functions, it is inevitable thatthe telecommunications systems continue to increase in size in terms ofboth hardware and software components. A bigger system requires a largeroverhead in terms of maintenance and testing functions as morecomponents need to be tested. If each existing and added component andtheir interconnects has to be individually tested, this overhead costcan increase exponentially, causing reduced throughput.

A need therefore exists for a telecommunications system which fulfillsthe distributed processing and multiservice demands described above, buthaving an architecture with messaging protocol which facilitates theopen distributed network environment and supports multiple services on acommon networking infrastructure. It is also desirous that the messagingprotocol efficiently addresses each component of the telecommunicationssystem and facilitates efficient processing, testing, and maintenancefunctions.

SUMMARY OF THE INVENTION

According to a preferred embodiment of the present invention, atelecommunications system is provided, having a network servicesprocessor (NSP) for handling telecommunications in conformance with apredefined signaling system and for distributing processing applicationsincluding call handling and routing to a plurality of platforms, eachplatform having a unique address and responds to application specificmessages, comprising: a plurality of packet managers (PMs) foraccessing, processing, and distributing packetized call data over apacket network; a plurality of media control platforms (MCPs) foraccessing, processing, and distributing media tasks (MCTs); a pluralityof interconnect controllers (ICCs) and corresponding plurality of localarea networks (LANs), each for interfacing the NSP with the plurality ofplatforms including the PMs and the MCPs through a corresponding LAN,wherein a message protocol (hiQ) is employed which encapsulates theapplication specific messages within a standard LAN protocol fordistribution among the plurality of platforms connected to the LANs.

Preferably, the hiQ protocol includes a unicast message frame whereinone of the plurality of platforms connected to the LANs is addressed.The plurality of LANs include at least one partner pair of LANs, actingas primary and redundant LANs in active and standby modes, the pluralityof platforms connected to the primary LAN being active in processingapplications and the plurality of platforms connected to the redundantLAN being in standby mode. The hiQ protocol includes a multicast messageframe wherein each of the plurality of platforms connected to thepartner pair LANs is addressed.

According to an aspect of the invention, the ICC includes means forswitching over a redundant LAN from standby to active upon determinationof a fault in a platform connected to the primary LAN. The hiQ protocolincludes a broadcast message frame wherein all of the plurality ofplatforms connected to the LANs is addressed, wherein the ICCdistributes a first broadcast message frame having a status requestbroadcasted to the plurality of platforms connected to the LANs, and theICC performs fault identification and location among the plurality ofplatforms by examining responses received from the plurality ofplatforms. The ICC determines a fault exists in a platform if theplatform fails to respond to the status request within a specifiedperiod of time. The ICC distributes a second broadcast message framewhich includes responses from all the plurality of platforms connectedto the LANs to provide a connectivity map of each of the plurality ofplatforms connected to the LANs. Preferably, the first broadcast messageframe and the second broadcast message frame are consecutive messageframes.

A method of message handling in a telecommunications system is alsoprovided, the telecommunications system having a network servicesprocessor (NSP) for accessing, processing, and distributingtelecommunications in conformance with a predefined signaling system andfor distributing processing applications including call handling androuting to a plurality of platforms, each platform having a uniqueaddress and responds to application specific messages, the methodcomprising: connecting the plurality of platforms to local area networks(LANs), the plurality of platforms include packet managers (PMs) foraccessing, processing, and distributing packetized call data over apacket network and a plurality of media control platforms (MCPs) foraccessing, processing, and distributing media tasks (MCTs); connectingthe LANs to a corresponding plurality of interconnect controllers(ICCs), each ICC for interfacing the NSP with the plurality of platformsthrough a corresponding LAN; and distributing application specificmessages to the plurality of platforms via a message protocol (hiQ)having a message frame which encapsulates application specific messageswithin a standard LAN protocol.

Preferably, the hiQ protocol includes an unicast message frame whereinone of the plurality of platforms connected to the LANs is addressed.The method preferably further including the step of assigning onepartner pair from the plurality of LANs to act as primary and redundantLANs in active and standby modes, the plurality of platforms connectedto the primary LAN being active in processing applications and theplurality of platforms connected to the redundant LAN being in standbymode. The hiQ protocol includes a multicast message frame wherein eachpair of the plurality of platforms connected to LANs are addressed.

The method preferably further including the step of switching over aredundant LAN from standby to active upon determination of a fault in aplatform connected to the primary LAN.

According to another embodiment of the present invention, the hiQprotocol includes a broadcast message frame wherein all of the pluralityof platforms connected to the LANs is addressed. The method furtherincluding the steps of distributing a first broadcast message framehaving a status request broadcasted to the plurality of platformsconnected to the LANs, and performing fault identification and locationamong the plurality of platforms by examining responses received fromthe plurality of platforms, and the step of distributing a secondbroadcast message frame which includes responses from all the pluralityof platforms connected to the LANs, wherein the first broadcast messageframe and the second broadcast message frame are consecutive messageframes. Preferably, the standard LAN protocol is UDP/IP and thepredefined signaling system is SS7.

BRIEF DESCRIPTION OF THE DRAWINGS

These and further features of the invention may be better understoodwith reference to the accompanying specification, drawings, and appendixdescribing preferred embodiments of the invention, in which:

FIG. 1 shows a block diagram of an hiQ architecture according to apreferred embodiment of the present invention;

FIG. 2 shows a block diagram of the interconnection between the NSP, ICCand the LANs according to a preferred embodiment of the presentinvention;

FIG. 3 shows a hiQ protocol message frame according to the presentinvention; and

FIG. 4 shows another hiQ protocol message frame according to the presentinvention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

According to an aspect of the present invention, an hiQ protocolencapsulates application messages within a standardized protocol andprovides the addressing capabilities to address all resources orplatforms connected to a centralized maintenance system with a singlemessage. The protocol allows addressing a single platform and a singleapplication running on that platform. For redundancy, the protocoladdresses a redundant pair of platforms and redundant pair ofapplications, and allows addressing a single unit and multipleapplications in each unit.

The hiQ architecture having a centralized maintenance system and methodis employed which monitors all connected resources or platforms bybroadcasting status requests to and receiving responses from eachconnected resource or platform, preferably in consecutive singlecentralized message frames. By monitoring the responses to the broadcastrequest, the centralized maintenance system can determine which unitsfailed by their failure to respond within a specified amount of time.The failed units can be reported as defective for alarming purposes.

According to a further aspect of the invention, the status responsemessage having the last set of responses is broadcasted to eachconnected unit. This allows each unit to have a complete “connectivity”map.

According to another aspect of the present invention, the monitoringsystem employs a redundant system where there are two units and twopaths for each application to ensure reliable operation. When one unitof the two partner pair fails, the redundant pair unit is switched overto complete the application. The hiQ protocol allows the delivery of asingle message to both members of the pair. This provides the neededsynchronization for units and processes.

FIG. 1 shows the basic hiQ architecture, which includes seven mainfunctional parts, namely, the Network Services Processor (NSP), theInter-Connect Controller (ICC), the Packet Manager (PM), distributedMedia Control Platforms (MCP), the Integrated Signaling Gateway[ISG-(SSNC)] and the connection medium which allows all of thefunctional blocks to communicate with one another. The connection mediumitself provides the seventh part as well, since it is split into twoentities, namely, the connection between the NSP and ICC and theconnection between the ICC and distributed platforms. Unlessspecifically stated otherwise, each of the main functional parts withinthe hiQ architecture preferably includes a Pentium-class processor andassociate memory for buffering data and storing software programs to beexecuted by the associated processor to implement accessing, processing,and distribution of applications. The architecture supports 4 000 000 ormore BHCA. However, for the purposes of call model calculation, itshould be taken into account that the initial offering will support 60000 trunks and the second step will support 250 000 trunks. A meanholding time of 180 s/call is used, therefore 60 000 trunks (30 000incoming and 30 000 outgoing) equates to 600 000 BHCA (or 167 calls/s).250 000 trunks (125 000 incoming and 125 000 outgoing) equates to 2 500000 BHCA (or 695 calls/s).

The NSP is preferably a digital switching system such as the EWSDCP113C, which is capable of handling call processing pursuant to callsignaling systems such as SS7. The NSP functions include providing thefeature/CALLP database, loading of necessary data to the distributedMCP's, distributing applications to the PMs and MCPs, and perform thosecoordinated functions necessary to keep the system running (e.g.maintenance, recovery, administration, alarming etc).

The Signaling System Network Control (SSNC) and the Integrated Signaling

Gateway (ISG) is part of the Signaling Platform (SP) for handling SS7links including

-   directly terminating SS7 links, routing incoming SS7 packets to NSP    or MCPs, routing outgoing SS7 packets to appropriate SS7    destination(s), and performing SS7 maintenance and SS7    administration functions.

The ICC provides a bi-directional interface between the NSP and thedistributed MCP's, PM, and Signaling Gateway. In addition to providingthe interface, it also provides the protocol conversion between standardEWSD messaging (e.g., MBU/MCH based addressing) and Ethernet MediaAccess Control (MAC) addressing. Thus, messaging within the hiQarchitecture can be provided via fast Ethernet (100 MB/s LANsegment(s)). The ICC also handles the routine test interface from theNSP. The ICC supervises the LAN interface and reports the connectionstatus of the distributed platforms to the NSP. The ICC also detects anyLAN faults and report any faults to the NSP. The ICC performsinter-platform routing for any distributed platform. Essentially, thismeans that whenever a peripheral platform (including MCP, PM, SignalingGateway) needs to communicate with a second (or multiple) peripheralplatform, the message is sent to the ICC and the ICC reroutes it to therequired destination. Advantageously, this feature offloads the NSPsince the above mentioned messages would normally be routed via the NSP.This bypass provides the NSP with additional capacity.

Referring to FIG. 2, which shows the interconnection between the ICCs,the NSP, and the LANs. The ICC includes an interface board for signalinginterface between CP113C (IOP:MB. This is an 8-bit parallel interface)and ICC. The interface board connects directly with a controller boardwhich acts as a multiplexer. One controller board supports up to 8interface connections and therefore by extension, 8 IOP:MB interfaces.If additional IOP:MB interfaces need to be supported, this isaccomplished by adding interface boards (which support up to 4interfaces) and/or controller boards. The application software (SW)communicates with the controller board via DMA (bi-directionally), sothat NSP messages may be received and sent. Lastly, the LAN controllerprovides the actual interface to the MCPs, PM, and Signaling Gateway.The application entity therefore provides the bi-directional connectionpath between the NSP format messages and the Ethernet messages. The ICCpreferably comprises a Pentium classed CPU.

The media control platform (MCP) provides a platform for media controlfunctions, which work with the software in the NSP to provide mediacontrol features. The MCP also provides a platform for MCP ManagerFunctions and performs Media Control Tasks (MCTs) running simultaneouslyunder a real-time operating system (VxWorks). Each Media Control Task isan independent call-processing entity. The NSP runs EWSD LTG software toprovide the MCT functions.

The MCP Manager Functions are distributed across the following tasks:Messaging task: This task is multi functional. It provides the interfaceto the Ethernet for communication between all tasks on the MCP and theNSP or other distributed platforms. It also provides an interface withthe ICC for maintenance of the LAN and the message channels associatedwith the Media Control Tasks.

SW Watchdog task: This task is responsible for monitoring all MCP tasksto ensure that each task is running correctly. MCT Loading & StartupTask: This task provides an interface to the NSP for loading of MCTsoftware. It is also responsible for managing and manipulating thecontext associated with each MCT, and for spawning each MCT task in itscorrect context.

MCP Maintenance Task: This task performs general maintenance functionson the MCP, including handling reset requests from the NSP, routine testand audit functions, utilities and processing firmware upgrades.

The packet manager (PM) provides the interface to the Media Gateway forthe hiQ architecture. The incoming signaling is done via ISUP (ISDN UserPart), BICC (Bearer Independent Call Control) and MGCP (Media GatewayControl Protocol) messaging. The PM platform preferably comprises acommercially available Sun FT1800 fault tolerant system. Connection tothe hiQ is done via redundant Ethernet paths on the internal LAN.Maintenance of the PM is by a periodic message sent from the NSP to thePM via each redundant LAN segment. The PM responds to this message oneach LAN side. The purpose of this messaging is two-fold in that itserves to inform the NSP that the PM is still available and secondly,the message from NSP to PM should contain the active LAN side so thatthe PM knows which LAN side to use when transmitting to the NSP and/orany other peripheral platform.

The interface between NSP and ICC is an 8-bit serial interface whichmimics the IOP:MB to Message Buffer interface. A Local Area Network(LAN) connects the ICC to the system periphery (MCP, PM, SP). Thisconnection is realized using a Fast Ethernet (100 MB/S) LAN segment.

The hiQ protocol is encapsulated in a standard protocol (e.g., Ethernetfor Release 1 & 2, UDP/IP from Release 3 on.). This allows fortransmission over a commercial LAN and LAN Switches. Advantageously, thehiQ protocol provides encapsulation to the application specificprotocols and messages, by providing transport services to theapplication.

According to a preferred embodiment of the present invention, the hiQprotocol includes message frames with encapsulation of applicationmessages in standard LAN protocol, such as Fast Ethernet. The use of astandard LAN protocol in the hiQ protocol according to the presentinvention facilitates the open distributed network environment thatsupports multiple services on a common networking infrastructure.

The Ethernet LAN supports the message transfer modes offered by the NSPin single out, collective out and broadcast out. The hiQ protocolprovides the addressing capabilities to address all units connected tothe LAN with a single message; allows addressing a single unit and asingle application running on that unit; allows addressing a redundantpair of units and redundant pair of applications; and allows addressinga single unit and multiple applications in each unit.

FIG. 3 shows a hiQ protocol communication frame having encapsulatedapplication task and standardized LAN protocol. Referring to FIG. 3, theEthernet type field is used to distinguish internal Ethernet messagesfrom other protocol based messages (e.g. SCTP). The hiQ header ispreferably a bitmap(8 bytes). The ICC uses this bitmap including theDestination MAC and Source MAC to inform the MCP to which applications(e.g., MCT's) to send the encapsulated command. The information in thedata field is the actual command or message information. Therefore, toaccomplish single outs (unicast), collective outs (multicast) orbroadcast outs, the unique board addresses are used with thecorresponding MCT bitmap set. Responses from each MCT are seen as astandard NSP message encapsulated within a MAC frame.

FIG. 4 shows a hiQ multicast communication frame. The multi-cast domainis used by the ICC, which employs a so called “flags” Ethernet frame(sent on each LAN side) to ensure that each MCP is accessible. Themessage is sent once and received by each MCP. The ICC sends thismessage every 100 ms. Included in this message is a bitmap of which MCPboards are currently active. The MCP can then use this information toensure that sync channel messages or reports are routed on the correctLAN side. Advantageously, the methodology according to the presentinvention provides a virtual link between ICC sides. In suchconfiguration, the failure of a single Ethernet on any board is known byall other boards. This bitmap includes the information of boards on thesecond LAN segment (where applicable). Preferably, the “flags” aredetected from the bit pattern H′7F7F in the data section of the frame.

If any board does not respond with a flag response within a preset timelimit, the ICC will retry the non-responsive boards. If there is stillno response, the ICC will issue a channel error per board with a bitmapto show how many MCT tasks are impacted. The error handling andappropriate action is then taken by the particular fault analysisprogram in the NSP.

Thus, the hiQ messaging protocol facilitates a centralized maintenancemaster, in this embodiment the ICC, to address all the units of thesystem connected to the corresponding LAN. Each individual unit respondsto the request. These responses provide centralized maintenance. Bymonitoring the response to the broadcast request, the maintenance master(the ICC) can determine units which fail to respond. These failing unitscan be reported as defective for alarming purposes.

By broadcasting the last set of responses—in one message, themaintenance master notifies all connected units of the status of therest. This allows each unit to have a complete “connectivity” map anduse this information for routing decision within the internalcommunication fabric.

The hiQ is a redundant system where there are always two units and twopaths to ensure reliable operation (single failure protection). The hiQmessaging protocol allows the distribution of a single message to thetwo partners of a redundant pair. The pair works in an ACTIVE/ACTIVE orACTIVE/STANDBY mode. ACTIVE/ACTIVE meaning both partners in theredundant pair are processing, in most cases different applications, butare receiving multicast messages so that one can be switched-over tocover the other. In ACTIVE/STANDBY, one of the partner pairs isprocessing in ACTIVE mode while the other is on STANDBY. The messagingsystem allows the delivery of a single message to both members of thepair. This provides the needed synchronization for units and processes.

The above-described test/monitoring method is also applicable totesting/monitoring the LANs. If all flag responses fail, the ICC sendsan additional LAN test message to its own Media Access Control (MAC)address. If the LAN test message is received, all MCP boards are markedas faulty (with the appropriate channel error messages being sent to theNSP). If the LAN test message is not received, the ICC reports a LANfailure to the NSP.

Each MCP has a MAC address which maps to the board number. Upon power upeach board detects its slot and shelf number. This informationtranslates into a mapped MAC address (the mapped addresses are common toeach system). For example, the addressing protocol may assign IPaddresses 224.xxx to 239.xxx for multicast messages and broadcastmessages beginning at 255.xxx. This mapping is also known by the ICC. Toaccomplish communication, the unique MAC addresses are used inconjunction with a multi-cast domain. Communication to one MCP board isaccomplished using a standard communication frame. Each MCP can carry upto 62 MCT's. Each MCT is numbered as X-Y where X is the MCP number and Yis the task number. For communications purposes and fault handlingpurposes, the TSG-LTG mapping is adapted to be MCP-MCT mapping.

Accordingly, applications such as MCTs performed by the MCPs and packetmanager tasks performed by the PMs are distributed and processing isdecentralized. On the other hand, fault location, monitoring, andreporting is centralized, through the ICC and LAN. The hiQ architectureaccording to the present invention provides redundancy via having twocopies of each component unit (side 0 and side 1). A failure of one unitautomatically causes a switchover to the secondary unit (without anyservice interruption). This is handled via the Fault Analysis SW runningon the NSP. Both LAN sides (LANO and LAN 1) are active but each carrieshalf the traffic using standard Line Trunk Group (LTG) message channeldistribution, i.e. each task has a different default active/standbyside. If a LAN failure occurs, the switchover causes the remaining LANto carry the full traffic load.

According to another embodiment of the present invention, the MCPssupports redundancy by distributing MCT's in such a way that each taskhas a partner which runs on a different MCP. That means that the failureof a single MCT results in its functionality being taken over by the“partner” board. Ultimately, this says that the failure of an MCP boardresults in the switchover of each MCT being carried by that board. TheSignal System Network Control (SSNC) redundancy is realized with eachunit (e.g. MPU) having a redundant partner. For example, the MP'sinclude two MPU's which run micro-synchronously.

The SSNC is used to perform the signaling gateway functionality. TheSSNC is a multi-processor system with its own Maintenance devices disksand optical devices. It is preferably “loosely coupled” to the NSP viaan ATM30 link. The SSNC performs the task of terminating the #7 from thenetwork and converting the signaling into hiQ compatible messaging. TheSSNC further controls the routing of messages to NSP or MCT's. Further,the SSNC will route #7 messages from the hiQ to the network. The SSNCterminates pure SS7 links or the SS7 links are replaced by SCTPassociations.

According to another aspect of the present invention relating to faultlocation/reporting, MCP failure cases reported to the NSP comprise(besides MCT task failures) platform task failures and failures of theentire board. Upon a platform task failure the MCP resets itself andreports the reset to the ICC. A failure of the board is either detectedby the a watchdog of the MCP (which leads to an MCP reset) or the ICCwhich sends periodic FLAGS commands to all MCPs. Unacknowledged FLAGScommands lead to a MCP board failure determination by the ICC. In bothcases the ICC informs the NSP via message channel errors and the NSPswitches the redundant MCP copy on. The affected MCT's are configuredaccordingly to the same state in a serial manner, depending on a LOADparameter entry (YES/NO). The MCP status is dependent on the states ofits MCT's, e.g., if the last MCT of an MCP is configured to PLA then theMCP also has to change to PLA.

According to an aspect of the present invention relating to alarmingfunctions, upon determination of a faulty component from the responsesfrom each of the units connected to the LAN, an alarm is triggered. TheMP collects all hiQ alarms. All alarms not generated on the SSNC sideare sent over from CP System Alarming to the MP. For local alarmrepresentation the MP contains an Alarm Indication Unit that is able topresent all alarms via Critical, Major and Minor indications includingrelays to the existing Alarm Interface Unit (AIU).

Sections 2.1.1, 2.1.2.2.2, 2.1.4, 3.1, 3.2, and 3.2.1.3 of theFunctional Specification SURPASS Release NN.N; P30310-A2745-Q001-04-7659are particularly pertinent to embodiments of the present invention.These sections are incorporated-by-reference herein.

Glossary and Abbreviations

ACT Active AMA Automatic Message Accounting AMP ATM Bridge Processor APSApplication Program System ARP Address Resolution Protocol ASCHKAcknowledge Segment Checksum (message from MCP to NSP) ATM AsynchronousTransfer Mode B:CMY Bus for Common Memory B:IOC Bus for IOC BAP BaseProcessor BHCA Busy Hour Call Attempts BICC Bearer Independent CallControl BIOS Basic Input/Output System CAF Console Alarms and Fans CALLPCall Processing Process CAP Call Processor CCG Central Clock GeneratorCCNC Common Channel Signaling Network Control CFS Call Feature ServerCHAC Channel Active (command from NSP to MCP) CHAR Channel Ready(message from MCP to NSP) CHAS Channel Active Switched (message from MCPto NSP) CHECK Checksum (command from NSP to MCP) CHON Channel On(command from MCP/ICC to MCP) CI Critical Indicator CLAC Clock Active(command from NSP to MCP) CMY Common Memory CoPL Commercial ComputingPlatform CORBA Common Object Request Brokerage Architecture COUConference Unit CP Coordination Processor CPCI Compact PCI CPU CentralProcessing Unit CR Code Receiver CRC Cyclic Redundancy Check DB DatabaseDIP Dual Inline Parallel DIU Digital Interface Unit DLU Digital LineUnit DMA Direct Memory Access DRAM Dynamic RAM EAI Emergency ActionInterface EMC Electromagnetic Charge ENM EWSD Network Manager EPROMErasable Programmable Read Only Memory EPSONE Equipment Practice forSiemens Solution O.N.E. EQN Equipment Number ES-IS EndSystem-to-Intermediate System EWSD Electronisches Wahlsystem Digital (=Digital Switching System) FDDI Fibre Distributed Data Interface FSFunctional Specification FTP File Transfer Protocol FW Firmware GDTGlobal Descriptor Table GDTR Global Descriptor Table Register GP GroupProcessor GUI Graphical User Interface HSRP Hot Standby Router ProtocolHW Hardware I/F Interface IC Integrated Circuit ICC Inter-ConnectController ICMP Internet Control Message Protocol ID Identifier IDCIInterim Defined Central Office Interface IDT Interrupt Descriptor TableIDTR Interrupt Descriptor Table Register IEEE Institute of Electricaland Electronic Engineers IETF Internet Engineering Task Force IFTRInterface Tracer IOC Input/Output Controller IOP Input/Output ProcessorIP Internet Protocol IRDP ICMP Router Discovery Protocol ISDN IntegratedServices Digital Network ISG Integrated Signaling Gateway (SSNC) ISTARTInitial Start ISUP ISDN Signaling User Part (SS7) ITU-T InternationalTelecommunications Protocol JC1 Job Code 1 LAN Local Area Network LAPDLink Access Procedure type D LED Light Emitting Diode LM Feature (fromthe German Leistungsmerkmal) LODAP Load Data Parameter (command from NSPto MCP) LST Line Status Table LTAC LTG Active (command from NSP to MCP)LTAS LTG Active Switched (message from MCP to NSP) LTG Line Trunk GroupLTU Line Trunk Unit MAC Media Access Control MB Message Buffer MB(B)Message Buffer Type B MBD Message Buffer Type D MBL Maintenance BlockedMBU Message Buffer Unit MBUL Message Buffer Unit: LTG MBUS MessageBuffer Unit: SGC MB/S Megabits per second MCH Message Channel MCP MediaControl Platform MCPM Media Control Platform Manager (VxWorks ShellManagement Tasks) MCT Media Control Tasks (Virtual LTG's) MG MediaGateway MGC Media Gateway Controller MGCC Media Gateway Call ControlMGCP Media Gateway Control Protocol MIB Managed Information Base MIOMaintenance I/O Channel MML Man-Machine Language MMN Maintenance ManualNumber MP Main Processor MPOA Multi Protocol Over ATM Ms MillisecondsMSG Message MTP Message Transfer Part NEBS Network Equipment-BuildingSystem NIC Network Interface Card NSP Network Services Processor NSTARTnNewstart n, n = 0, 1, 2, 3 NVM Non Volatile Memory OAM&P Operations,Administration, Maintenance and Provisioning OC3 Optical Carrier 3 OEMOriginal Equipment Manufacturer OpEt Open Platform EWSD Transport OSOperating System OSI Open Systems Interconnection OSPF Open ShortestPath First OSS Operations Support System OST Operating State PAREN LoadData Parameter Received (message from MCP to NSP) PC Personal ComputerPCI Peripheral Component Interconnect PCU Packet Control Unit PDHPlesiochronous Digital Hierarchy PLA Planned PM Packet Manager PRAC MCTRecovery Acknowledgement (message from MCP to NSP) RAM Random AccessMemory RCP Remote Control Processor RCU Remote Control Unit RCVR RecoverMCT (command from NSP to MCP) RES Restorable RFC Request for Comment RIPRouting Information Protocol ROM Read Only Memory RSU Remote SwitchingUnit SBC Single Board Computer SC Smart Commander SCCS Switching ControlCenter System SCTP Stream Control Transmission Protocol SDC SecondaryDigital Carrier SDH Synchronous Digital Hierarchy SDRAM Single DataRandom Access Memory SG Signaling Gateway SGC Switch Group Control SIPACSiemens Package System SLST Service LST SN Switching Network SNMPSimplified Network Management Protocol SPSB Switching PeripherySimulator B Board (Controller) SPSC Switching Periphery Simulator CBoard (Interface) SPSD Switching Periphery Simulator D Board (Port) SPSESwitching Periphery Simulator E Board (Converter) SPSF SwitchingPeriphery Simulator F Board (Frame) SS Subsystem SSG Space Stage GroupSSNC Signaling System Network Control SS7 Signaling System No. 7 STAFStandard Failure STM1 Synchronous Transfer Mode, Level 1 SW Software SWOSwitchover SYNC MCT-MCT Synchronization Channel SYP System Panel T1Transmission Signal Level 1 TCP Transmission Control Protocol TDM TimeDivision Multiplexed TERE Test Result (message from MCT to NSP) TSG TimeStage Group TTL Transistor Transistor Logic UDP User Datagram ProtocolUNA Unavailable USB Universal Serial Bus UTP Unshielded Twisted PairVLAN Virtual LAN VoA Voice over ATM VoATM Voice over ATM VoIP Voice overIP VRRP Virtual Router Redundancy Protocol WAN Wide Area Network WMWorld Market

Although illustrative embodiments of the present invention have beendescribed herein with reference to the accompanying drawings, it is tobe understood that the present invention is not limited to those preciseembodiments, and that various other changes and modifications may beaffected therein by one skilled in the art without departing from thescope or spirit of the present invention. All such changes andmodifications are intended to be included within the scope of theinvention as defined by the appended claims.

1. A telecommunications system having a network services processor (NSP)for handling telecommunications in conformance with a predefinedsignaling system and for distributing processing applications includingcall handling and routing to a plurality of platforms, each platformhaving a unique address and responds to application specific messages,comprising: a plurality of packet managers (PMs) for accessing,processing, and distributing packetized call data over a packet network;a plurality of media control platforms (MCPs) for accessing, processing,and distributing media tasks (MCTs); a plurality of interconnectcontrollers (ICCs) and corresponding plurality of local area networks(LANs), each for interfacing the NSP with the plurality of platformsincluding the PMs and the MCPs through a corresponding LAN, wherein amessage protocol (hiQ) is employed which encapsulates the applicationspecific messages within a standard LAN protocol for distribution amongthe plurality of platforms connected to the LANs.
 2. The system of claim1, wherein the hiQ protocol includes a unicast message frame wherein oneof the plurality of platforms connected to the LANs is addressed.
 3. Thesystem of claim 1, wherein the plurality of LANs include at least onepartner pair of LANs, acting as primary and redundant LANs in active andstandby modes, the plurality of platforms connected to the primary LANbeing active in processing applications and the plurality of platformsconnected to the redundant LAN being in standby mode.
 4. The system ofclaim 1, wherein the hiQ protocol includes a multicast message framewherein each pair of the plurality of platforms connected to the LANsare addressed.
 5. The system of claim 4, wherein the ICC includes meansfor switching over a redundant LAN from standby to active upondetermination of a fault in a platform connected to the primary LAN. 6.The system of claim 1, wherein the hiQ protocol includes a broadcastmessage frame wherein all of the plurality of platforms connected to theLANs is addressed.
 7. The system of claim 1, wherein the ICC distributesa first broadcast message frame having a status request broadcasted tothe plurality of platforms connected to the LANs, and the ICC performsfault identification and location among the plurality of platforms byexamining responses received from the plurality of platforms.
 8. Thesystem of claim 7, wherein the ICC determines a fault exists in aplatform if the platform fails to respond to the status request within aspecified period of time.
 9. The system of claim 7, wherein the ICCdistributes a second broadcast message frame which includes responsesfrom all the plurality of platforms connected to the LANs to provide aconnectivity map of each of the plurality of platforms connected to theLANs.
 10. The system of claim 9, wherein the first broadcast messageframe and the second broadcast message frame are consecutive messageframes.
 11. A method of message handling in a telecommunications systemhaving a network services processor (NSP) for accessing, processing, anddistributing telecommunications in conformance with a predefinedsignaling system and for distributing processing applications includingcall handling and routing to a plurality of platforms, each platformhaving a unique address and responds to application specific messages,the method comprising: connecting the plurality of platforms to localarea networks (LANs), the plurality of platforms include packet managers(PMs) for accessing, processing, and distributing packetized call dataover a packet network and a plurality of media control platforms (MCPS)for accessing, processing, and distributing media tasks (MCTs);connecting the LANs to a corresponding plurality of interconnectcontrollers (ICCs), each ICC for interfacing the NSP with the pluralityof platforms through a corresponding LAN; and distributing applicationspecific messages to the plurality of platforms via a message protocol(hiQ) having a message frame which encapsulates application specificmessages within a standard LAN protocol.
 12. The method of claim 11,wherein the hiQ protocol includes an unicast message frame wherein oneof the plurality of platforms connected to the LANs is addressed. 13.The method of claim 11, further including assigning one partner pairfrom the plurality of LANs to act as primary and redundant LANs inactive and standby modes, the plurality of platforms connected to theprimary LAN being active in processing applications and the plurality ofplatforms connected to the redundant LAN being in standby mode.
 14. Themethod of claim 13, wherein the hiQ protocol includes a multicastmessage frame wherein each pair of the plurality of platforms connectedto the LANs are addressed.
 15. The method of claim 14, further includingthe step of switching over a redundant LAN from standby to active upondetermination of a fault in a platform connected to the primary LAN. 16.The method of claim 11, wherein the hiQ protocol includes a broadcastmessage frame wherein all of the plurality of platforms connected to theLANs is addressed.
 17. The method of claim 11, further including thesteps of distributing a first broadcast message frame having a statusrequest broadcasted to the plurality of platforms connected to the LANs,and performing fault identification and location among the plurality ofplatforms by examining responses received from the plurality ofplatforms.
 18. The method of claim 17, wherein the fault is identifiedand located when a platform fails to respond to the status requestwithin a specified amount of time.
 19. The method of claim 17, furtherincluding the step of distributing a second broadcast message framewhich includes responses from all the plurality of platforms connectedto the LANs.
 20. The method of claim 19, wherein the first broadcastmessage frame and the second broadcast message frame are consecutivemessage frames.
 21. The method of claim 11, wherein the standard LANprotocol is UDP/IP.
 22. The method of claim 11, wherein the predefinedsignaling system is SS7.